Near field communication detection in wireless charging systems

ABSTRACT

This disclosure describes systems, methods, and apparatus related to near field communication (NFC) detection. A device may determine a first device in proximity to a charging area of the device. The device may detect a presence of a first NFC device in proximity to the charging area of the device. The device may determine the first NFC device is associated with the first device. The device may determine to transition the device to one or more operating modes based at least in part on the presence of the first NFC device.

TECHNICAL FIELD

This disclosure generally relates to systems and methods for wirelesscharging stations, more particularly, to near field communication (NFC)detection in wireless charging systems.

BACKGROUND

Wireless charging or inductive charging uses a magnetic field totransfer energy between devices. Wireless charging may be implemented ata charging station. Energy is sent from one device to another devicethrough an inductive coupling. The inductive coupling is used to chargebatteries or run a device. Power is delivered through non-radiative,near field, magnetic resonance from a power transmitting unit (PTU) to apower receiving unit (PRU).

An NFC device is a device that may operate in accordance with a set ofstandards that establishes radio communication to communicate withanother proximate NFC device. In some instances, an NFC device mayinclude an NFC tag or maybe associated with an NFC tag.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a network diagram illustrating an example networkenvironment for near field communication (NFC) detection, in accordancewith one or more example embodiments of the present disclosure.

FIG. 2 depicts an illustrative PRU static parameter, in accordance withone or more example embodiments of the present disclosure.

FIGS. 3A-3B depict illustrative PTU operation modes tables, inaccordance with one or more embodiments of the disclosure.

FIGS. 4A-4B depict illustrative flow diagrams for NFC detection, inaccordance with one or more example embodiments of the presentdisclosure.

FIG. 5A illustrates a flow diagram of an illustrative process for NFCdetection, in accordance with one or more embodiments of the disclosure.

FIG. 5B illustrates a flow diagram of an illustrative process for NFCdetection, in accordance with one or more embodiments of the disclosure.

FIG. 6 illustrates a functional diagram of an example communicationstation that may be suitable for use as a user device, in accordancewith one or more example embodiments of the disclosure.

FIG. 7 illustrates a block diagram of an example machine upon which anyof one or more techniques (e.g., methods) may be performed, inaccordance with one or more embodiments of the disclosure.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

A power transmitting unit (PTU) may transmit power wirelessly to chargeone or more power receiving units (PRUs). The PTU's current conductedthrough its coil generates a magnetic field. PRUs placed in thismagnetic field convert the magnetic field into a voltage that is usedfor powering the device or charging the battery. PRUs placed in thePTU's magnetic field area send back their operation information to thePTU during various stages of wireless charging. For example, during ahandshake procedure, where a PRU may advertise its capabilities to thePTU. The one or more PRUs placed in the PTU's magnetic field area sendback their operation information to the PTU. Such information mayinclude a PRU's rectifier voltage and the rectifier current, among otherparameters.

With the advancement in computing devices, an increasing number ofdevices supporting NFC may also require wireless charging. Such devicesmay utilize one or more NFC tags in order to take advantage of NFCtechnology. An NFC device may be a device that includes an interface forcommunicating over the air. An example of such a device is a mobiledevice. The application of NFC technology can be extended to anincreased variety of devices and is not limited to mobile devices. Forexample, an NFC device may be a lamp or other devices. Wireless chargingmay adversely affect an NFC tag because of its form-function. Generally,NFC tags do not require batteries. The NFC tags get their power fromjust being near a powered NFC device (e.g., a mobile device). The NFCtags get their power from an active device (e.g., a mobile device)generating a magnetic field which induces an electric current in theantenna of the passive device (e.g., the NFC tag) which powers up theNFC chip. The NFC tag then creates a further magnetic field, which canin return be read by the active device (e.g., the mobile device)allowing data to be transferred. The NFC tag may be internal to an NFCdevice (e.g., inside a lamp) or may be external (e.g., on a poster).Exposing an NFC tag to the wireless charging of the PTU may overheat theNFC tag and may damage its circuitry including its NFC chip.

Example embodiments of the present disclosure relate to systems,methods, and devices for NFC detection.

In one embodiment, a PTU may transition from an operational state to afault state based at least in part on a determination of an NFC tag.Typically, the PTU may be configured to operate in one or more states.For example, the PTU may be in a PTU power save state, a PTU low-powerstate, a PTU power transfer state, etc. these states may be based atleast in part on a wireless charging standard such as the AirFuelAlliance (AFA) wireless charging standard or any other wireless chargingstandard. The fault state may prevent the PTU from sending power todevices that may be in proximity of the PTU. This may prevent the NFCtag from being damaged by exposing the NFC tag to the wireless chargingof the PTU. Further, this may prevent an interruption to the wirelesscharging when a device contains NFC tags that are supported andprotected from the wireless charge.

In one embodiment, in order for the PTU to determine when to transitionto the fault state, the PTU may analyze PRU information received from aPRU that may be associated with an NFC device (e.g., an NFC tag). ThePRU may transmit during, for example, a handshake procedure with thePTU, PRU static information including, but not limited to, whether theNFC device is supported and protected by the PRU.

In one embodiment, the PRU information may include an NFC bit that maybe set based at least in part, on whether NFC is supported and/orprotected on a PRU. For example, after the PRU sets the NFC bit to “0,”or “1,” the PRU may send the PRU information that includes the set NFCbit to the PTU. The PTU may receive the PRU information on an interfacefor communicating over the air. The PTU may decode the PRU informationand may extract the NFC bit. The extracted NFC bit may be set, forexample, to either “0” or “1.”

In one embodiment, the PTU may determine whether the NFC bit is set to“0” or “1,” in order to determine whether to transition to a fault stateor not. For example, if the NFC bit is set to “0” in the PRU informationreceived from the PRU, the PTU may determine whether an NFC tag isdetected in the proximity of the PTU or not. If the PTU detects an NFCtag, the PTU may transition to a fault state, such as a latching faultstate or a local fault state. A latching fault state may be a faultstate that may impact the wireless charging system, including, devicesinvolved in the wireless charging system such as PRUs, PTU, or any otherdevices involved in the wireless charging system. A local fault statemay be a fault state that affects the PTU.

In one embodiment, if the PTU determines that the NFC bit is set to “1,”the PTU may determine whether an NFC tag or other NFC devices aredetected. In that case, if the PTU does detect an NFC tag or other NFCdevices, then the PTU may not transfer to a fault state. If the PTU hadalready detected the NFC tag or other NFC devices, and the PTU hadalready transitioned to a fault state due to the detection of the NFCtag or other NFC devices, the PTU may clear the fault and may resumenormal operation.

In one embodiment, if the PTU detects an NFC tag or other NFC devices,the PTU may listen for messages (e.g., advertising messages, etc.) thatare typically received from a PRU. The advertising messages may includeinformation that may determine that the device sending the advertisingmessages is a PRU and not an NFC tag. In the case that the PTU does notreceive a valid advertising message after a predetermined time, the PTUmay determine that detected NFC tag is not protected and therefore thePTU may transition to a fault state in order to prevent damaging the NFCtag.

The above descriptions are for purposes of illustration and are notmeant to be limiting. Numerous other examples, configurations,processes, etc., may exist, some of which are described in greaterdetail below. Example embodiments will now be described with referenceto the accompanying figures.

FIG. 1 depicts a network diagram illustrating an example networkenvironment for NFC detection, in accordance with one or more exampleembodiments of the present disclosure, which may include one or moreuser devices 120 and a wireless power transmitting unit (PTU) 102. Theone or more user devices 120 may be power receiving units (PRUs)operable by one or more user(s) 110. While FIG. 1 shows PRUs including alaptop 128 and smart devices 124 and 126, the disclosed principles arenot limited thereto and may include any device capable of wirelesscharging (e.g., a lamp).

In some embodiments, the user devices 120 and the PTU 102 may includeone or more computer systems similar to that of the functional diagramof FIG. 6 and/or the example machine/system of FIG. 7.

The user device(s) 120 (e.g., 124, 126, or 128) may be capable of beingwirelessly charged. The user device(s) 120 (e.g., 124, 126, or 128) mayinclude any suitable processor-driven device including, but not limitedto, a mobile device or a non-mobile, e.g., a static, device. Forexample, user device(s) 120 may include, a user equipment (UE), astation (STA), an access point (AP), a personal computer (PC), awearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), adesktop computer, a mobile computer, a laptop computer, an Ultrabook™computer, a notebook computer, a tablet computer, a server computer, ahandheld computer, a handheld device, an internet of things (IoT)device, a sensor device, a PDA device, a handheld PDA device, anon-board device, an off-board device, a hybrid device (e.g., combiningcellular phone functionalities with PDA device functionalities), aconsumer device, a vehicular device, a non-vehicular device, a portabledevice, a non-portable device, a lamp, and intelligent device, a mobilephone, a cellular telephone, a PCS device, a PDA device whichincorporates a wireless communication device, a mobile or portable GPSdevice, a DVB device, a relatively small computing device, a non-desktopcomputer, a “carry small live large” (CSLL) device, an ultra mobiledevice (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID),an “origami” device or computing device, a device that supportsdynamically composable computing (DCC), a context-aware device, a videodevice, an audio device, an A/V device, a set-top-box (STB), a blu-raydisc (BD) player, a BD recorder, a digital video disc (DVD) player, ahigh definition (HD) DVD player, a DVD recorder, a HD DVD recorder, apersonal video recorder (PVR), a broadcast HD receiver, a video source,an audio source, a video sink, an audio sink, a stereo tuner, abroadcast radio receiver, a flat panel display, a personal media player(PMP), a digital video camera (DVC), a digital audio player, a speaker,an audio receiver, an audio amplifier, a gaming device, a data source, adata sink, a digital still camera (DSC), a media player, a smartphone, atelevision, a music player, or the like.

Any of the user device(s) 120 (e.g., user devices 124, 126, 128), theNFC tag 142, and the PTU 102 may be configured to communicate with eachother directly or via one or more communications networks 130 and/or 135wirelessly or wired. The direct communication may include Bluetooth LowEnergy (BLE), in-band modulation, or the like. Any of the communicationsnetworks 130 and/or 135 may include, but not limited to, any one of acombination of different types of suitable communications networks suchas, for example, broadcasting networks, cable networks, public networks(e.g., the Internet), private networks, wireless networks, cellularnetworks, or any other suitable private and/or public networks. Further,any of the communications networks 130 and/or 135 may have any suitablecommunication range associated therewith and may include, for example,global networks (e.g., the Internet), metropolitan area networks (MANs),wide area networks (WANs), local area networks (LANs), or personal areanetworks (PANs). In addition, any of the communications networks 130and/or 135 may include any type of medium over which network traffic maybe carried including, but not limited to, coaxial cable, twisted-pairwire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwaveterrestrial transceivers, radio frequency communication mediums, whitespace communication mediums, ultra-high frequency communication mediums,satellite communication mediums, or any combination thereof.

Any of the user device(s) 120 (e.g., user devices 124, 126, 128), theNFC tag 142, and the PTU 102 may include one or more communicationsantennas. Communications antenna may be any suitable type of antennacorresponding to the communications protocols used by the user device(s)120 (e.g., user devices 124, 126 and 128), the NFC tag 142, and the PTU102. Some non-limiting examples of suitable communications antennasinclude Wi-Fi antennas, Institute of Electrical and ElectronicsEngineers (IEEE) 802.11 family of standards compatible antennas,directional antennas, non-directional antennas, dipole antennas, foldeddipole antennas, patch antennas, multiple-input multiple-output (MIMO)antennas, or the like. The communications antenna may be communicativelycoupled to a radio component to transmit and/or receive signals, such ascommunications signals to and/or from the user devices 120.

Any of the user devices 120 (e.g., user devices 124, 126, 128), the NFCtag 142, and the PTU 102 may include any suitable radio and/ortransceiver for transmitting and/or receiving radio frequency (RF)signals in the bandwidth and/or channels corresponding to thecommunications protocols utilized by any of the user device(s) 120 theNFC tag 142, and the PTU 102 to communicate with each other. The radiocomponents may include hardware and/or software to modulate and/ordemodulate communications signals according to pre-establishedtransmission protocols. The radio components may further have hardwareand/or software instructions to communicate via one or more Wi-Fi and/orWi-Fi direct protocols, as standardized by the Institute of Electricaland Electronics Engineers (IEEE) 802.11 standards. In certain exampleembodiments, the radio component, in cooperation with the communicationsantennas, may be configured to communicate via 2.4 GHz channels (e.g.802.11b, 802.11g, 802.11n, 802.11ax), 5 GHz channels (e.g. 802.11n,802.11ac, 802.11ax), or 60 GHZ channels (e.g. 802.11ad). In someembodiments, non-Wi-Fi protocols may be used for communications betweendevices, such as Bluetooth, dedicated short-range communication (DSRC),Ultra-High Frequency (UHF) (e.g. IEEE 802.11af, IEEE 802.22), white bandfrequency (e.g., white spaces), or other packetized radiocommunications. The radio component may include any known receiver andbaseband suitable for communicating via the communications protocols.The radio component may further include a low noise amplifier (LNA),additional signal amplifiers, an analog-to-digital (A/D) converter, oneor more buffers, and digital baseband.

NFC is a wireless communication technology similar to Wi-Fi orBluetooth. Typically, NFC is used to transfer data from one device tothe other. For example, NFC may be used to transfer data from an NFCenabled mobile device to another NFC enabled mobile device, from amobile device to a payment terminal or from an NFC tag to a mobilephone.

A simple way to use NFC technology may be a phone picking up informationfrom a ‘tag’, usually embedded in a sticker, a wristband, a poster, abusiness card, a badge, or the like. In some examples, an NFC tag may beincluded within a user device and not external to the user device. NFCtags may contain small microchips with little antenna(s), which canstore a small amount of information for transfer to another NFC device,such as a mobile phone. A tag may be programmed with one or more tasksbased using, for example, an application running on a user device. Withthe tag created, the NFC tag may be placed, for example, at a desk atwork. A user device may be swiped over the tag in order to receive theprogrammed information.

Different data types may be stored on an NFC tag. The actual amount ofdata varies depending on the type of NFC tag used, that is, differentNFC tags may have different memory capacities. Usually, information isstored in a specific data format so that it can be reliably read by mostdevices and mobile phones.

Generally, NFC tags do not require batteries. NFC tags get their powerfrom just being near a powered NFC device (e.g., a mobile device). NFCTags work by an active device (e.g., a mobile device) generating amagnetic field which induces an electric current in the antenna of thepassive device (e.g., the NFC Tag) which powers up the NFC Chip. The NFCTag then creates a further magnetic field, which can in return be readby the active device (e.g., the mobile device) allowing data to betransferred.

In one embodiment, the PTU 102 may include a transmitting coil (e.g.,coil 140), and the PRUs (e.g., user devices 120) may include a receivingcoil. For example, energy may be transmitted from the transmitting coilto the receiving coil, by electromagnetic induction between the twocoils. This may cause the transmission of charging power from the PTU tothe PRU in response to determining that the PRU is located within thecharging area. The PTU may communicate with a PRU to receiveinformation, such as identification information, power received, powerneeded, location, etc.

In one embodiment, a PRU may advertise its information using one or morecommunication protocols. For example, the PRU may utilize communicationprotocols, such as bluetooth low energy (BLE), in-band modulation, orthe like, to advertise or transfer its PRU information to a PTU. The PRUinformation may contain static or dynamic PRU parameters. It isunderstood that although advertisement is done through BLE or in-bandmodulation, any other communication protocols that may be used forcommunicating between two devices may be used.

In one embodiment, the PTU 102 may transition from an operational stateto a fault state based at least in part on a detection of the NFC tag142, which may be internal or external to a user device 120. In thisexample of FIG. 1, the NFC tag 142 is shown as being internal to userdevice 124. In other examples, the NFC tag 142 may be external (e.g., abracelet, etc.) to the user device 124. Typically, the PTU 102 may beconfigured to operate in one or more states. For example, the PTU 102may be in a PTU power save state, a PTU low-power state, a PTU powertransfer state, etc. These states may be based at least in part on awireless charging standard such as the AirFuel Alliance (AFA) wirelesscharging standard or any other wireless charging standard. The faultstate may prevent the PTU from sending power to devices (e.g., the NFCtag 142) that may be in proximity of the PTU. This may prevent the NFCtag 142 from being damaged from exposure to the wireless charging of thePTU 102.

In one embodiment, during a discovery procedure (e.g., a handshakeprocedure, etc.) between user devices 120 and PTU 102, the user devices120 may send information to the PTU 102. For example, if user device 124is in need of wireless charging, the user device 124 may advertise thatrequest to the PTU 102 or the user device 124 may receive anadvertisement from PTU 102 that the PTU 102 is capable of performing theservice of wirelessly charging the user device 124. The user device 124and the PTU 102 may perform, for example, a handshake procedure that maycommunicate to the PTU 102 information associated with user device 124.The information may include various bits that are set based on theconfiguration of the user device 124. In order for the PTU 102 todetermine when to transition to the fault state, the PTU 102 may analyzeinformation received from the user device 124. The information mayinclude information associated with the NFC tag 142. The user device 124may transmit, for example, during the handshake procedure with the PTU,PRU static information including, but not limited to, whether an NFC tag(e.g., NFC tag 142) is supported and protected in the user device 124.

In one embodiment, the PTU 102 may receive the information including anNFC bit that may be set based at least in part on whether NFC issupported and/or protected on the user device 124. For example, afterthe user device 124 sets the NFC bit to “0,” or “1,” the user device 124may send the information that includes the set NFC bit to the PTU 102.The PTU 102 may receive the information on an interface forcommunicating over the air. The PTU 102 may decode that information andmay extract the NFC bit. The extracted NFC bit may be set to either “0”or “1.” Based on the value of the NFC bit, the PTU 102 may transition(or not transition) to a different working state. For example, if theNFC bit is set to “0” in the information received from the user device124, the PTU 102 may determine whether an NFC tag is detected in theproximity of the PTU or not. If the PTU 102 detects an NFC tag, the PTU102 may transition to a fault state, such as a latching fault state or alocal fault state. A latching fault state may be a fault state that mayimpact the wireless charging system, including, devices involved in thewireless charging system such as PRUs (e.g., user devices 120), PTU 102,or any other devices involved in the wireless charging system. A localfault state may be a fault state that affects the PTU 102.

In one embodiment, if the PTU 102 determines that the NFC bit is set to“1,” the PTU 102 may determine whether an NFC tag 142 is detected. Inthat case, if the PTU does detect an NFC tag 142, then the PTU 102 maynot transfer to a fault state and may continue its normal operation. Ifthe PTU 102 had already detected the NFC tag 142, and the PTU 102 hadalready transitioned to a fault state due to the detection of the NFCtag 142, the PTU 102 may clear the fault and may resume normaloperation.

In one embodiment, if the PTU 102 detects the NFC tag 142, and the PTU102 does not receive a valid advertising or discover messages after apredetermined time, the PTU 102 may determine that detected NFC tag 142is not protected and therefore the PTU 102 may transition to a faultstate in order to prevent damaging the NFC tag. For example, if the PTU102 detects the NFC tag 142 and does not receive a valid advertisementafter 0.2 seconds, the PTU 102 may determine that the NFC tag 142 is notassociated with a user device 120 and is an external NFC tag that maynot be protected against wireless charging. In order to prevent exposureof the NFC tag 142 to the wireless charging of the PTU 102, the PTU 102may transition to a fault state (e.g., latching fault state or localfault state). This will stop the PTU 102 from sending power to the NFCtag 142, which could have resulted in damaging the NFC tag 142. It isunderstood that the above descriptions are for purposes of illustrationand are not meant to be limiting.

FIG. 2 depicts an illustrative PRU static parameter, in accordance withone or more example embodiments of the present disclosure.

Generally, a PRU may contain information, including data and parametersthat the PRU may exchange with a PTU during the wireless charging of thePRU. Such information may assist the PTU in determining how towirelessly charge the PRU. For example, a PRU static parametercharacteristic element may contain, at least in part, static data thatmay be set on a PRU. The PRU static parameter characteristic element maybe intended to enable a PTU to read the static data from the PRU. A PRUmay communicate the static data using one or more fields associated withthe static parameter characteristic element. An example field of the oneor more fields may be the PRU information field, which may be used toidentify one or more operational modes of the PRU.

Referring to FIG. 2, there is shown a bit field for PRU informationfield 200. The PRU information field 200 may contain one or more bitsthat may be set based at least in part on the PRU. The PRU informationfield 200 may include one or more bit fields, such as, an NFC receiverbit 202, a power control algorithm preference, an adjust powercapability, a charge complete connected mode, a PTU test mode, and oneor more bits that may be reserved for future use (RFU). For example, theNFC receiver bit 202 may contain information related to one or more NFCdevices that may be associated with the PRU. For example, if the NFCreceiver bit 202 is set to “1,” this may indicate to the PTU that NFC issupported and/or protected. However, if the NFC receiver bit 202 is setto “0,” then this may indicate to the PTU that NFC is not supportedand/or not protected. For example, if a PRU is associated with an NFCtag or other NFC devices, which are supported and/or protected, the PRUmay set the NFC receiver bit 202 to “1.” The PTU receiving thatinformation may determine that the PRU include or is associated with anNFC tag or other NFC devices. An associated NFC tag or other NFC devicesmay be included in the PRU or may be external to the PRU.

In one embodiment, a PTU may transition its operating mode based ondetermining the value of the NFC receiver bit 202. The PTU maytransition to a fault state or may continue normal operation based onthe value of the received NFC receiver bit 202. For example, if the NFCreceiver bit 202 is set to “0” in the PRU information received from thePRU, the PTU may determine whether an NFC tag is detected in theproximity of the PTU or not. If the PTU detects an NFC tag, the PTU maytransition to a fault state, such as a latching fault state or a localfault state. A latching fault state may be a fault state that may impactthe wireless charging system, including, devices involved in thewireless charging system such as PRUs, PTU, or any other devicesinvolved in the wireless charging system. A local fault state may be afault state that affects the PTU.

In one embodiment, if the PTU determines that the NFC receiver bit 202is set to “1,” the PTU may determine whether an NFC tag or other NFCdevices are detected. In that case, if the PTU does detect an NFC tag orother NFC devices, then the PTU may not transfer to a fault state. Ifthe PTU had already detected the NFC tag or other NFC devices, and thePTU had already transitioned to a fault state due to the detection ofthe NFC tag or other NFC devices, the PTU may clear the fault and mayresume normal operation.

In one embodiment, if the PTU detects an NFC tag or other NFC devices,the PTU may listen for messages that are typically received from a PRU.For example, an advertising message may be received from the PRU. Theadvertising message may include information that may determine that thedevice sending the advertising message is a PRU and not an NFC tag. Inthe case that the PTU does not receive a valid advertisement after apredetermined time, the PTU may determine that the detected NFC tag isnot supported and/or protected and therefore the PTU may transition to afault state in order to prevent damaging the NFC tag or the other NFCdevices.

FIGS. 3A-3B depict illustrative PTU operation modes tables 300 and 350respectively, in accordance with one or more embodiments of thedisclosure.

Referring to FIG. 3A, the PTU operation modes table 300 may containconditions for transitioning a PTU between one or more operation modesor states. The one or more operation modes or states may include, butnot limited to, a PTU power save, a PTU low power, a PTU power transfer,PTU latching fault, PTU local fault, or the like. The one or moreoperations modes or states may be power modes or states. For example, aPTU may have an original state of PTU power save and may transition toPTU low power based on one or more conditions that may be optional orrequired.

In one embodiment, the PTU may transition to a PTU latching fault or aPTU local fault based on one or more conditions. The one or moreconditions may be set in accordance with a standard, a systemadministrator, a manufacturer of the PTU and/or the PRU, userpreferences, etc. For example, condition 302 may include one or moreconditions for transitioning the PTU from an origin state to adestination state, when the condition 302 is met. The condition 302 maybe required or may be optional based at least in part on a setting inaccordance with a standard, a system administrator, or a user. Condition302 may indicate that the PTU may transition to a fault state whencondition 302 is met. According to an exemplary condition 302, if thePTU detects an NFC tag or other NFC devices, the PTU may listen foradvertising messages that are typically received from a PRU. Theadvertising messages may include information that may determine that thedevice sending the advertising messages is a PRU and not an NFC tag. Inthe case that the PTU does not receive a valid advertising message aftera predetermined time, the PTU may determine that the detected NFC tag isnot protected, and therefore the PTU may transition to a fault state(e.g., a PTU latching fault or a PTU local fault) in order to preventdamaging the NFC tag or the other NFC devices. It is understood thatthis condition 302 is a non-limiting example of a condition totransition the PTU between an origin state and a destination state.Other conditions may be determined in order to transition the PTU to afault state based on whether an NFC tag or other NFC devices weredetected or not detected.

Referring to FIG. 3B, the PTU operation modes table 350 may containconditions for transitioning a PTU between one or more operation modesor states. The one or more operation modes or states may include, butnot limited to, a PTU power save, a PTU low power, a PTU power transfer,PTU latching fault, PTU local fault, or the like. These one or moreoperations modes or states may be power modes or states. For example, aPTU may have an original state of PTU power save and may transition toPTU low power based on one or more conditions that may be optional orrequired.

In one embodiment, the PTU may transition its operating mode based oncondition 304 that may be associated with an NFC receiver bit on thePRU. For example, the PRU may set the NFC receiver bit in the PRU staticparameter characteristic, which may be sent to the PTU. Under condition304, the PTU may transition to a fault state or may continue normaloperation based on the value of the NFC receiver bit. For example,condition 304 indicates that if the NFC receiver bit is set to “0” inthe PRU information received from the PRU, the PTU may determine whetheran NFC tag or another NFC device is detected in the proximity of the PTUor not. If the PTU detects an NFC tag or another NFC device, the PTU maytransition to a fault state, such as a latching fault state or a localfault state. A latching fault state may be a fault state that may impactthe wireless charging system, including, devices involved in thewireless charging system such as PRUs, PTU, or any other devicesinvolved in the wireless charging system. A local fault state may be afault state that affects the PTU.

In one embodiment, other conditions may be utilized to transition or nottransition the PTU from an origin state to a destination state. Forexample, if the PTU determines that the NFC receiver bit is set to “1,”the PTU may then determine whether an NFC tag or other NFC devices aredetected. In that case, if the PTU does detect an NFC tag or other NFCdevices, then the PTU does not transfer to a fault state. If the PTU hadalready detected the NFC tag or other NFC devices, and the PTU hadalready transitioned to a fault state due to the detection of the NFCtag or other NFC devices, the PTU may clear the fault and may resumenormal operation in case the NFC receiver bit is set to “1.” It isunderstood that the above descriptions are for purposes of illustrationand are not meant to be limiting.

FIGS. 4A-4B depicts illustrative flow diagrams for NFC detection, inaccordance with one or more example embodiments of the presentdisclosure.

Referring to FIG. 4A, there is shown a flow diagram for NFC detectionthat may facilitate determining the transition of a PTU (e.g., PTU 102of FIG. 1) one or more operation modes or states. For example, an NFCdetection system may facilitate the transition of one or more operationmodes of a PTU based at least in part on one or more conditions. The oneor more operation modes may include, but not limited to, a PTU powersave, a PTU low power, a PTU power transfer, PTU latching fault, PTUlocal fault, or the like. These one or more operations modes or statesmay be power modes or states. The one or more conditions made include,but not limited to, detection of NFC devices, analysis of data receivedfrom one or more PRUs in the proximity of the PTU, or other conditionsset in accordance to a standards, a system administrator, a manufacturerof the PTU and/or the PRU, user preferences, etc.

A PTU may detect the presence of one or more devices that may be inproximity of its charging surface. The PTU may utilize one or morediscovery procedures to discover devices in its proximity. For example,the PTU may determine whether one or more PRUs, e.g., (user devices 120of FIG. 1) require to be wirelessly charged by the PTU. The one or PRUsmay include, or may be associated with, one or more NFC devices (e.g.,NFC tags). The PTU may also discover the one or more PRUs in theproximity of the PTU based on received messages from the one or morePRUs. For example, the PTU may receive advertisement messages, servicerequest messages or handshake messages, or the like from these PRUs.Based on the discovered devices, the PTU may determine whether tocontinue normal operation (e.g., wirelessly charging devices) or maydetermine whether to transition to other states or modes, such as faultstates.

In one embodiment, in order for the PTU to determine when to transitionto the fault state, the PTU may analyze PRU information received from aPRU (e.g., user devices 120 of FIG. 1) that may be associated with anNFC device (e.g., an NFC tag). The PRU may transmit during, for example,the handshake procedure with the PTU, PRU static information including,but not limited to, whether an NFC device is supported and/or protectedby the PRU.

In one embodiment, the PRU information may include an NFC bit (e.g., NFCreceiver bit) that may be set based at least in part on whether NFC issupported and/or protected by the PRU. For example, after the PRU setsthe NFC receiver bit to “0” or “1,” the PRU may send the PRU informationthat includes the set NFC receiver bit to the PTU that may be providingthe wireless charge. The PTU may receive the PRU information on aninterface for communicating over the air. The PTU may decode the PRUinformation and may extract the NFC receiver bit. The extracted NFCreceiver bit may be set to either “0” or “1.” Based at least in part onthe value of the NFC receiver bit, the PTU may transition (or nottransition) to a different operational state. The NFC receiver bit maycontain information related to an NFC device. For example, if the NFCreceiver bit is set to “1,” this may indicate to the PTU that NFC issupported and/or protected. However, if the NFC receiver bit is set to“0,” then this may indicate to the PTU that NFC is not supported and/ornot protected.

Referring to FIG. 4A, an NFC detection flow diagram may start andproceed to block 402.

At block 402, the PTU may determine whether the NFC receiver bit is setto “1” or “0.” The PTU may transition its operating mode based ondetermining the value of the NFC receiver bit. The PTU may transition toa fault state or may continue normal operation based on the value of theNFC receiver bit.

At block 404, in case the PTU determines that the NFC receiver bit isset to “0,” in the PRU information received from the PRU, the PTU maydetermine whether an NFC device is detected in the proximity of the PTUor not.

At block 406, if the PTU detects an NFC device, the PTU may transitionto a fault state, such as a latching fault state or a local fault state.A latching fault state may be a fault state that may impact the wirelesscharging system, including, devices involved in the wireless chargingsystem such as PRUs, PTU, or any other devices involved in the wirelesscharging system. A local fault state may be a fault state that affectsthe PTU. Transitioning to a fault state prevents the PTU from chargingthe detected NFC device, which is not protected according to the NFCreceiver bit being equal to “0.”

At block 408, if the PTU did not detect an NFC device in the proximityto the PTU, then the PTU does not need to transition to a fault stateand may continue normal operation.

If at block 402, the PTU determines that the NFC receiver bit is equalto “1,” the PTU may determine whether an NFC device is detected (block410). If the PTU does not detect an NFC device at block 410, the PTUdoes not need to transition to a fault state and may continue normaloperation (block 408).

If at block 410 the PTU determined that an NFC device was detected, thePTU may then analyze its operation mode or state, for example, todetermine whether the PTU is in a PTU power save, a PTU low power, a PTUpower transfer, a PTU latching fault, a PTU local fault, or the like.

At block 412, the PTU may determine whether it is in a fault mode orstate (e.g., a latching fault or a local fault). In case the PTUdetermines that it is not in a fault mode or state, the PTU may not needto transition to another state and may continue normal operation (block408). However, if the PTU does determine that it is in a fault state,the PTU may then clear the fault mode or state and transition to anothermode or state (block 414). Since the NFC receiver bit is set to “1,” itindicates that the NFC device is supported and/or protected. Further,since the NFC device was detected by the PTU, then the PTU does not needto be in a fault state. Therefore, if the PTU, under those conditions,was in a fault state, the PTU may clear the fault mode and transition toanother mode or state (e.g., a PTU power save, a PTU low power, a PTUpower transfer, etc.).

The PTU may restart the process periodically or based on a predeterminedinterval set in accordance to a communication standard, a userpreference, a system administrator, etc.

Referring to FIG. 4B, an NFC detection flow diagram may start andproceed to block 430.

At block 430, the PTU may determine whether an NFC device (e.g., an NFCtag) is detected in proximity to the PTU. The PTU may detect thepresence of an NFC device based at least in part on a discoveryprocedure used to discover devices in proximity to the charging surfacearea of the PTU. A discovery procedure may include scanning devices thatare within range of the charging field of the PTU. The PTU may alsodiscover devices in proximity to the PTU based on advertisementmessages, service request messages, handshake messages, or the like thatmay be received from these devices. Receiving any of these messages mayindicate to the PTU whether additional information corresponding to thedetected NFC device exists or not.

At block 432, if the PTU does not detect at least one NFC device, thePTU may not transition to a fault mode or state. That is the PTU maycontinue its operation using one of the operation modes. In that case,the PTU continues to charge devices that are in proximity to the PTU'scharging surface.

If the PTU detects at least one NFC device, the PTU may determine atblock 434 whether advertisement messages, service request messages, orhandshake messages are received from any devices in the proximity of thePTU. As explained above, these types of messages may include PRU staticinformation that may assist the PTU in determining whether to transitionbetween the one or more operation modes. The PTU may wait for apredetermined time to receive at least one of the above messages. Forexample, if the PTU after a few seconds (e.g., 0.2 seconds) does notreceive at least one of the above messages, the PTU may then determinethat a message is not received.

If after the predetermined time, the PTU may determine that a message isnot received from any PRUs in the proximity of the PTU. Consequently, atblock 436, since an NFC device was detected (block 430) and no messagewas received from a PRU (block 434), then the PTU may determine that theNFC device is not associated with a PRU and may determine to transitionto a fault state or mode (e.g., latching fault and/or local fault). Inthat case, the PTU may stop generating charging power that may causedamage to the detected NFC devices.

If the PTU does receive a message from at least one PRU, at block 438,the PTU may extract the PRU static information that may be encoded inthe received message. The PTU may determine whether the detected NFCdevice is associated with the PRU that sent the message to the PTU. Forexample, if the PTU receives an advertisement message from a PRU, thePTU may extract the PRU static information from the advertisementmessage in order to determine whether the NFC receiver bit is set to “1”or “0.” The PTU may also extract information that may determine that thedetected NFC device is associated with the PRU. If the PTU determinesthat the NFC receiver bit is set to “0,” then the PTU may haveessentially determined that an NFC device is detected, that the NFCdevice is associated with the PRU, and the PRU information included inthe received message from the PRU indicated that the NFC receiver bit isset to a value that does not support and/or protect the NFC device. Inthat case, the PTU may transition to a fault state (block 436) in orderto prevent the detected NFC device from being damaged by the powergenerated by the PTU.

If the NFC receiver bit is set to “1,” then the PTU may determine thatthe detected NFC device is supported and/or protected by the PRU thatsent the message to the PTU. In that case, the PTU at block 432 may notneed to transition to a fault state and may continue operating andwirelessly charging devices in proximity to it charging service.

The PTU may restart the process periodically or based on a predeterminedinterval set in accordance to a communication standard, a userpreference, a system administrator, etc.

FIG. 5A illustrates a flow diagram of illustrative process 500 for NFCdetection, in accordance with one or more embodiments of the disclosure.

At block 502, a PTU (e.g., PTU 102 of FIG. 1) may determine the presenceof a PRU (e.g., user devices 120 of FIG. 1) in proximity to a chargingarea of the PTU. For example, the PTU may detect the presence of a PRUthat may be in proximity of its charging surface. The PTU may utilizeone or more discovery procedures to discover devices in its proximity.For example, the PTU may determine whether a PRU requires to bewirelessly charged by the PTU. The PRU may include, or may be associatedwith, one or more NFC devices (e.g., NFC tags). The PTU may alsodiscover the PRU in the proximity of the PTU based on received messagesfrom the PRU. For example, the PTU may receive advertisement messages,service request messages or handshake messages, or the like from thePRU.

At block 504, the PTU may detect the presence of an NFC device (e.g.,NFC tag) in proximity to the charging area of the PRU. For example, thePTU may utilize the discovery procedures or other procedures in order todetect whether an NFC device is in the proximity of the PTU. In someembodiments, the PTU may detect the presence of an NFC device based onthe discovered PRU. For example, during a handshake procedure betweenthe PRU and the PTU, the PRU may send information to the PTU. The PRUand the PTU may perform handshake procedure that may communicate to thePTU information associated with PRU. The information may include variousbits that are set based on the configuration of the PRU. In order forthe PTU to determine when to transition to the fault state, the PTU mayanalyze information received from the PRU. The information may includeinformation associated with the NFC device. The PRU may transmit during,for example, the handshake procedure to the PTU, PRU static informationincluding, but not limited to, whether in NFC device is supported andprotected in the PRU.

At block 506, the PTU may determine that the NFC device is associatedwith the PRU. If the PTU determines that the NFC devices is associatedwith the PRU, then the PTU may have to determine additional informationsince an NFC device is detected by the PTU. For example, the PTU mayutilize the information received from the PRU, which may include, but isnot limited to, an NFC receiver bit that may be sent by the PRU. The NFCreceiver bit may be set to either “0” or “1.” For example, if the NFCreceiver bit is set to “0,” then the PTU may determine that the detectedNFC device is not protected and may not be supported by the PRU. In thatcase, the PTU may have to determine whether to continue charging or stopcharging devices in proximity to the PTU. If the NFC receiver bit is setto “1,” then the PTU may determine that the detected NFC device isprotected and is supported by the PRU. In that case, the PTU maycontinue performing its operation (e.g., wirelessly charging devices).

At block 508, the PTU may determine to transition the PTU to one or moreoperating modes based at least in part on the presence of the NFCdevice. The PTU may determine whether to continue normal operation(e.g., wirelessly charging devices) or may determine whether totransition to other states or modes, such as fault states.

FIG. 5B illustrates a flow diagram of illustrative process 550 for NFCdetection, in accordance with one or more embodiments of the disclosure.

At block 552, a PRU (e.g., user devices 120 of FIG. 1) may determine thepresence of a PTU (e.g., PTU 102 of FIG. 1). The PTU may include asurface area that be used to charge one or more PRUs. The PTU's currentconducted through its coil generates a magnetic field such that when thePRU is placed in the PTU's magnetic field area, the PRU may bewirelessly charged.

At block 554, the PRU may determine one or more device data (e.g., PRUstatic information), including an NFC receiver bit that may be set bythe PRU before sending a message to the PTU. The message may include,but is not limited to, a handshake message, an advertisement message, aservice request message, or the like. When the PRU is placed in thePTU's magnetic field area, the PRU may send its operation information tothe PTU during various stages of the wireless charging. For example,during a handshake procedure, the PRU may advertise its capabilities tothe PTU.

At block 556, the PRU may include the one or more device data into themessage before sending the message to the PTU. In order to include theone or more device data into the message, the PTU may encode the one ormore data into the message. The one or more device data may include PRUstatic information (e.g., PRU information 200 of FIG. 2). An NFCreceiver bit may contain information related to NFC devices that may beassociated with the PRU. For example, if the NFC receiver bit is set to“1,” this may indicate to the PTU that NFC is supported and/or protectedby the PRU. However, if the NFC receiver bit is set to “0,” then thismay indicate to the PTU that NFC is not supported and/or not protected.

At block 558, the PRU may then send the message to the PTU. The PRU maysend the message to the PTU using one or more communication standards(e.g., BLE, Wi-Fi, in-band modulation, etc.). The message may include atleast in part the value of the NFC receiver bit that may have beenencoded and or set by the PRU in the one or more device data. The PTUmay receive the one or more data from PRU. The one or more data maydetermine that the PRU includes or is associated with an NFC tag orother NFC devices. An associated NFC tag or other NFC devices may beincluded in the PRU or may be external to the PRU. The process mayrepeat periodically, in accordance to a standard, a systemadministrator, or user preferences, etc. It is understood that the abovedescriptions are for purposes of illustration and are not meant to belimiting.

FIG. 6 shows a functional diagram of an exemplary communication station600 in accordance with some embodiments. In one embodiment, FIG. 6illustrates a functional block diagram of a communication station thatmay be suitable for use as an PTU 102 (FIG. 1) or a user device 120(FIG. 1) in accordance with some embodiments. The communication station600 may also be suitable for use as a handheld device, a mobile device,a cellular telephone, a smartphone, a tablet, a netbook, a wirelessterminal, a laptop computer, a wearable computer device, a femtocell, ahigh data rate (HDR) subscriber station, an access point, an accessterminal, or other personal communication system (PCS) device.

The communication station 600 may include communications circuitry 602and a transceiver 610 for transmitting and receiving signals to and fromother communication stations using one or more antennas 601. Thecommunications circuitry 602 may include circuitry that can operate thephysical layer (PHY) communications and/or medium access control (MAC)communications for controlling access to the wireless medium, and/or anyother communications layers for transmitting and receiving signals. Thecommunication station 600 may also include processing circuitry 606 andmemory 608 arranged to perform the operations described herein. In someembodiments, the communications circuitry 602 and the processingcircuitry 606 may be configured to perform operations detailed in FIGS.1-5B.

In accordance with some embodiments, the communications circuitry 602may be arranged to contend for a wireless medium and configure frames orpackets for communicating over the wireless medium. The communicationscircuitry 602 may be arranged to transmit and receive signals. Thecommunications circuitry 602 may also include circuitry formodulation/demodulation, upconversion/downconversion, filtering,amplification, etc. In some embodiments, the processing circuitry 606 ofthe communication station 600 may include one or more processors. Inother embodiments, two or more antennas 601 may be coupled to thecommunications circuitry 602 arranged for sending and receiving signals.The memory 608 may store information for configuring the processingcircuitry 606 to perform operations for configuring and transmittingmessage frames and performing the various operations described herein.The memory 608 may include any type of memory, including non-transitorymemory, for storing information in a form readable by a machine (e.g., acomputer). For example, the memory 608 may include a computer-readablestorage device, read-only memory (ROM), random-access memory (RAM),magnetic disk storage media, optical storage media, flash-memory devicesand other storage devices and media.

In some embodiments, the communication station 600 may be part of aportable wireless communication device, such as a personal digitalassistant (PDA), a laptop or portable computer with wirelesscommunication capability, a web tablet, a wireless telephone, asmartphone, a wireless headset, a pager, an instant messaging device, adigital camera, an access point, a television, a medical device (e.g., aheart rate monitor, a blood pressure monitor, etc.), a wearable computerdevice, or another device that may receive and/or transmit informationwirelessly.

In some embodiments, the communication station 600 may include one ormore antennas 601. The antennas 601 may include one or more directionalor omnidirectional antennas, including, for example, dipole antennas,monopole antennas, patch antennas, loop antennas, microstrip antennas,or other types of antennas suitable for transmission of RF signals. Insome embodiments, instead of two or more antennas, a single antenna withmultiple apertures may be used. In these embodiments, each aperture maybe considered a separate antenna. In some multiple-input multiple-output(MIMO) embodiments, the antennas may be effectively separated forspatial diversity and the different channel characteristics that mayresult between each of the antennas and the antennas of a transmittingstation.

In some embodiments, the communication station 600 may include one ormore of a keyboard, a display, a non-volatile memory port, multipleantennas, a graphics processor, an application processor, speakers, andother mobile device elements. The display may be an LCD screen includinga touch screen.

Although the communication station 600 is illustrated as having severalseparate functional elements, two or more of the functional elements maybe combined and may be implemented by combinations ofsoftware-configured elements, such as processing elements includingdigital signal processors (DSPs), and/or other hardware elements. Forexample, some elements may include one or more microprocessors, DSPs,field-programmable gate arrays (FPGAs), application specific integratedcircuits (ASICs), radio-frequency integrated circuits (RFICs) andcombinations of various hardware and logic circuitry for performing atleast the functions described herein. In some embodiments, thefunctional elements of the communication station 600 may refer to one ormore processes operating on one or more processing elements.

Certain embodiments may be implemented in one or a combination ofhardware, firmware, and software. Other embodiments may also beimplemented as instructions stored on a computer-readable storagedevice, which may be read and executed by at least one processor toperform the operations described herein. A computer-readable storagedevice may include any non-transitory memory mechanism for storinginformation in a form readable by a machine (e.g., a computer). Forexample, a computer-readable storage device may include read-only memory(ROM), random-access memory (RAM), magnetic disk storage media, opticalstorage media, flash-memory devices, and other storage devices andmedia. In some embodiments, the communication station 600 may includeone or more processors and may be configured with instructions stored ona computer-readable storage device memory.

FIG. 7 illustrates a block diagram of an example machine 700 or systemupon which any one or more of the techniques (e.g., methodologies)discussed herein may be performed. In other embodiments, the machine 700may operate as a standalone device or may be connected (e.g., networked)to other machines. In a networked deployment, the machine 700 mayoperate in the capacity of a server machine, a client machine, or bothin server-client network environments. In an example, the machine 700may act as a peer machine in peer-to-peer (P2P) (or other distributed)network environments. The machine 700 may be a personal computer (PC), atablet PC, a set-top box (STB), a personal digital assistant (PDA), amobile telephone, a wearable computer device, a web appliance, a networkrouter, a switch or bridge, or any machine capable of executinginstructions (sequential or otherwise) that specify actions to be takenby that machine, such as a base station. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein, such as cloud computing, software asa service (SaaS), or other computer cluster configurations.

Examples, as described herein, may include or may operate on logic or anumber of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operationswhen operating. A module includes hardware. In an example, the hardwaremay be specifically configured to carry out a specific operation (e.g.,hardwired). In another example, the hardware may include configurableexecution units (e.g., transistors, circuits, etc.) and acomputer-readable medium containing instructions where the instructionsconfigure the execution units to carry out a specific operation when inoperation. The configuring may occur under the direction of theexecution units or a loading mechanism. Accordingly, the execution unitsare communicatively coupled to the computer-readable medium when thedevice is operating. In this example, the execution units may be amember of more than one module. For example, under operation, theexecution units may be configured by a first set of instructions toimplement a first module at one point in time and reconfigured by asecond set of instructions to implement a second module at a secondpoint in time.

The machine (e.g., computer system) 700 may include a hardware processor702 (e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 704 and a static memory 706, some or all of which may communicatewith each other via an interlink (e.g., bus) 708. The machine 700 mayfurther include a power management device 732, a graphics display device710, an alphanumeric input device 712 (e.g., a keyboard), and a userinterface (UI) navigation device 714 (e.g., a mouse). In an example, thegraphics display device 710, the alphanumeric input device 712, and theUI navigation device 714 may be a touch screen display. The machine 700may additionally include a storage device (i.e., drive unit) 716, asignal generation device 718 (e.g., a speaker), an NFC detection device719, a network interface device/transceiver 720 coupled to antenna(s)730, and one or more sensors 728, such as a global positioning system(GPS) sensor, a compass, an accelerometer, or other sensor. The machine700 may include an output controller 734, such as a serial (e.g.,universal serial bus (USB), parallel, or other wired or wireless (e.g.,infrared (IR), near field communication (NFC), etc.) connection tocommunicate with or control one or more peripheral devices (e.g., aprinter, a card reader, etc.)).

The storage device 716 may include a machine-readable medium 722 onwhich is stored one or more sets of data structures or instructions 724(e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 724 may alsoreside, completely or at least partially, within the main memory 704,within the static memory 706, or within the hardware processor 702during execution thereof by the machine 700. In an example, one or anycombination of the hardware processor 702, the main memory 704, thestatic memory 706, or the storage device 716 may constitutemachine-readable media.

The NFC detection device 719 may carry out or perform any of theoperations and processes (e.g., processes 500 and 550) described andshown above. For example, the NFC detection device 719 may be configuredto facilitate a PTU to transition from a working state to a fault statebased at least in part on a determination of an NFC device, such as anNFC tag.

The NFC detection device 719 may be configured to analyze PRUinformation received from a PRU that may be associated with an NFCdevice (e.g., an NFC tag). The NFC detection device 719 may beconfigured to transmit during, for example, the handshake procedure withthe PTU, PRU static information including, but not limited to, whetherthe NFC device is supported and protected by the PRU.

The NFC detection device 719 may be configured to include PRUinformation, including but not limited to an NFC bit that may be setbased at least in part, on whether NFC is supported and/or protected ona PRU. For example, after the NFC bit is set to “0,” or “1,” the NFCdetection device 719 may be configured to send the PRU information thatincludes the set NFC bit to the PTU. The NFC detection device 719 may beconfigured to receive the PRU information on an interface forcommunicating over the air. The NFC detection device 719 may beconfigured to decode the PRU information and may be configured toextract the NFC bit. The extracted NFC bit may be set to either “0” or“1.” Based on the value of the NFC bit, the NFC detection device 719 maybe configured to transition (or not transition) the PTU to a differentworking state.

The NFC detection device 719 may be configured to determine whether theNFC bit is set to “0” or “1,” in order to determine whether totransition to a fault state or not. For example, if the NFC bit is setto “0” in the PRU information received from the PRU, the NFC detectiondevice 719 may be configured to determine whether an NFC tag is detectedin the proximity of the PTU or not. If an NFC device is detected, theNFC detection device 719 may be configured to transition the PTU to afault state, such as a latching fault state or a local fault state. Alatching fault state may be a fault state that may impact the wirelesscharging system, including, devices involved in the wireless chargingsystem such as PRUs, PTU, or any other devices involved in the wirelesscharging system. A local fault state may be a fault state that affectsthe PTU.

The NFC detection device 719 may be configured to determine whether anNFC tag or other NFC devices are detected if it is determined that theNFC bit is set to “1.” In that case, if an NFC tag or other NFC devicesis not detected, then the NFC detection device 719 may not transfer thePTU to a fault state. If the PTU had already detected the NFC tag orother NFC devices, and the PTU had already transitioned to a fault statedue to the detection of the NFC tag or other NFC devices, the NFCdetection device 719 may clear the fault on the PTU and may resumenormal operation.

The NFC detection device 719 may be configured to listen for advertisingmessages that may be typically received from a PRU. The advertisingmessages may include information that may determine that the devicesending the advertising messages is a PRU and not an NFC tag. In thecase that the PTU does not receive a valid advertisement after apredetermined time, the NFC detection device 719 may be configured todetermine that detected NFC tag is not protected and therefore the PTUmay transition to a fault state in order to prevent damaging the NFCtag.

While the machine-readable medium 722 is illustrated as a single medium,the term “machine-readable medium” may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 724.

Various embodiments may be implemented fully or partially in softwareand/or firmware. This software and/or firmware may take the form ofinstructions contained in or on a non-transitory computer-readablestorage medium. Those instructions may then be read and executed by oneor more processors to enable performance of the operations describedherein. The instructions may be in any suitable form, such as but notlimited to source code, compiled code, interpreted code, executablecode, static code, dynamic code, and the like. Such a computer-readablemedium may include any tangible non-transitory medium for storinginformation in a form readable by one or more computers, such as but notlimited to read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; a flash memory, etc.

The term “machine-readable medium” may include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine 700 and that cause the machine 700 to perform any one ormore of the techniques of the present disclosure, or that is capable ofstoring, encoding, or carrying data structures used by or associatedwith such instructions. Non-limiting machine-readable medium examplesmay include solid-state memories and optical and magnetic media. In anexample, a massed machine-readable medium includes a machine-readablemedium with a plurality of particles having resting mass. Specificexamples of massed machine-readable media may include non-volatilememory, such as semiconductor memory devices (e.g., electricallyprogrammable read-only memory (EPROM), or electrically erasableprogrammable read-only memory (EEPROM)) and flash memory devices;magnetic disks, such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 724 may further be transmitted or received over acommunications network 726 using a transmission medium via the networkinterface device/transceiver 720 utilizing any one of a number oftransfer protocols (e.g., frame relay, internet protocol (IP),transmission control protocol (TCP), user datagram protocol (UDP),hypertext transfer protocol (HTTP), etc.). Example communicationsnetworks may include a local area network (LAN), a wide area network(WAN), a packet data network (e.g., the Internet), mobile telephonenetworks (e.g., cellular networks), plain old telephone (POTS) networks,wireless data networks (e.g., Institute of Electrical and ElectronicsEngineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16family of standards known as WiMax®), IEEE 802.15.4 family of standards,and peer-to-peer (P2P) networks, among others. In an example, thenetwork interface device/transceiver 720 may include one or morephysical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or moreantennas to connect to the communications network 726. In an example,the network interface device/transceiver 720 may include a plurality ofantennas to wirelessly communicate using at least one of single-inputmultiple-output (SIMO), multiple-input multiple-output (MIMO), ormultiple-input single-output (MISO) techniques. The term “transmissionmedium” shall be taken to include any intangible medium that is capableof storing, encoding, or carrying instructions for execution by themachine 700 and includes digital or analog communications signals orother intangible media to facilitate communication of such software. Theoperations and processes (e.g., processes 500 and 550) described andshown above may be carried out or performed in any suitable order asdesired in various implementations. Additionally, in certainimplementations, at least a portion of the operations may be carried outin parallel. Furthermore, in certain implementations, less than or morethan the operations described may be performed.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. The terms “computing device,” “userdevice,” “communication station,” “station,” “handheld device,” “mobiledevice,” “wireless device” and “user equipment” (UE) as used hereinrefers to a wireless communication device such as a cellular telephone,a smartphone, a tablet, a netbook, a wireless terminal, a laptopcomputer, a femtocell, a high data rate (HDR) subscriber station, anaccess point, a printer, a point of sale device, an access terminal, orother personal communication system (PCS) device. The device may beeither mobile or stationary.

As used within this document, the term “communicate” is intended toinclude transmitting, or receiving, or both transmitting and receiving.This may be particularly useful in claims when describing theorganization of data that is being transmitted by one device andreceived by another, but only the functionality of one of those devicesis required to infringe the claim. Similarly, the bidirectional exchangeof data between two devices (both devices transmit and receive duringthe exchange) may be described as “communicating,” when only thefunctionality of one of those devices is being claimed. The term“communicating” as used herein with respect to a wireless communicationsignal includes transmitting the wireless communication signal and/orreceiving the wireless communication signal. For example, a wirelesscommunication unit, which is capable of communicating a wirelesscommunication signal, may include a wireless transmitter to transmit thewireless communication signal to at least one other wirelesscommunication unit, and/or a wireless communication receiver to receivethe wireless communication signal from at least one other wirelesscommunication unit.

As used herein, unless otherwise specified, the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicates that different instances of like objects arebeing referred to and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

The term “access point” (AP) as used herein may be a fixed station. Anaccess point may also be referred to as an access node, a base station,or some other similar terminology known in the art. An access terminalmay also be called a mobile station, user equipment (UE), a wirelesscommunication device, or some other similar terminology known in theart. Embodiments disclosed herein generally pertain to wirelessnetworks. Some embodiments may relate to wireless networks that operatein accordance with one of the IEEE 802.11 standards.

Some embodiments may be used in conjunction with various devices andsystems, for example, a personal computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, apersonal digital assistant (PDA) device, a handheld PDA device, anon-board device, an off-board device, a hybrid device, a vehiculardevice, a non-vehicular device, a mobile or portable device, a consumerdevice, a non-mobile or non-portable device, a wireless communicationstation, a wireless communication device, a wireless access point (AP),a wired or wireless router, a wired or wireless modem, a video device,an audio device, an audio-video (A/V) device, a wired or wirelessnetwork, a wireless area network, a wireless video area network (WVAN),a local area network (LAN), a wireless LAN (WLAN), a personal areanetwork (PAN), a wireless PAN (WPAN), and the like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, apersonal communication system (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableglobal positioning system (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a multiple input multiple output (MIMO) transceiver ordevice, a single input multiple output (SIMO) transceiver or device, amultiple input single output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, digitalvideo broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a smartphone, awireless application protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems following one or morewireless communication protocols, for example, radio frequency (RF),infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM(OFDM), time-division multiplexing (TDM), time-division multiple access(TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS),extended GPRS, code-division multiple access (CDMA), wideband CDMA(WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA,multi-carrier modulation (MDM), discrete multi-tone (DMT), Bluetooth®,global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra-wideband(UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G,3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long termevolution (LTE), LTE advanced, enhanced data rates for GSM Evolution(EDGE), or the like. Other embodiments may be used in various otherdevices, systems, and/or networks.

According to example embodiments of the disclosure, there may be adevice. The device may include at least one memory that storescomputer-executable instructions; and at least one processor of one ormore processors configured to access the at least one memory, whereinthe at least one processor is configured to execute thecomputer-executable instructions to determine a first device inproximity to a charging area of the device; detect a presence of a firstNFC device in proximity to the charging area of the device; determinethe first NFC device is associated with the first device; and determineto transition the device from a first operating mode to a secondoperating mode based at least in part on the presence of the first NFCdevice.

The implementations may include one or more of the following features.The first operating mode and the second operating mode include at leastin part a power transmitting unit (PTU) power save, PTU low power, PTUpower transfer, PTU latching fault, or PTU local fault. The at least oneprocessor may be further configured to execute the computer-executableinstructions to receive a first message from the first device on acommunication interface; and extract device data encoded in the firstmessage. The instructions to determine to transition the device mayfurther includes the instructions to determine a first message is notreceived from the first device within a predetermined time; anddetermine the second operating mode is at least one of a powertransmitting unit (PTU) latching fault or a PTU local fault mode. Thecommunication interface is in accordance with Bluetooth low energy(BLE), near field communication (NFC), in-band modulation, or Wi-Fi. Theextracted device data include one or more power receiving unit (PRU)static data, wherein the PRU static data includes at least in part anNFC receiver bit. The instructions to determine to transition the devicemay further includes the instructions to determine the NFC receiver bitis set to a first value; and determine the second operating mode is atleast one of a power transmitting unit (PTU) latching fault or a PTUlocal fault mode. The at least one processor may be further configuredto execute the computer-executable instructions to determine the NFCreceiver bit is set to a second value; determine an operating mode ofthe device is a power transmitting unit (PTU) latching fault mode or aPTU local fault mode; and transition the operating mode of the devicefrom the PTU latching fault mode or the PTU local fault mode to at leastone of a PTU power save, a PTU low power, or a PTU power transfer. Thedevice may further include a transceiver configured to transmit andreceive wireless signals. The device may further comprise one or moreantennas coupled to the transceiver.

According to example embodiments of the disclosure, there may be anon-transitory computer-readable medium storing computer-executableinstructions which, when executed by a processor, cause the processor toperform operations. The operations may include determining a presence ofa power transmitting unit (PTU); determining one or more device data,including a near field communication (NFC) receiver bit; encoding theone or more device data into a first message; and causing to send thefirst message to the PTU on a communication interface.

The implementations may include one or more of the following features.The communication interface is in accordance with bluetooth low energy(BLE), near field communication (NFC), in-band modulation, or Wi-Fi. ThePTU may include a wireless charging surface. The computer-executableinstructions cause the processor to further perform operationscomprising encoding the NFC receiver bit based on an association with afirst NFC device. The computer-executable instructions cause theprocessor to further perform operations comprising setting the NFCreceiver bit to indicate that the first NFC device is supported orprotected. The computer-executable instructions cause the processor tofurther perform operations comprising setting the NFC receiver bit toindicate that the first NFC device is not supported or not protected.

According to example embodiments of the disclosure, there may include amethod. The method may include determining, by at least one processor, afirst device in proximity to a charging area of a second device;detecting, by the at least one processor, a presence of a first NFCdevice in proximity to the charging area of the second device;determining, by the at least one processor, the first NFC device isassociated with the first device; and determining, by the at least oneprocessor, to transition the second device from a first operating modeto a second operating mode based at least in part on detecting thepresence of the first NFC device.

The implementations may include one or more of the following features.The first operating mode and the second operating mode include at leastin part a power transmitting unit (PTU) power save, PTU low power, PTUpower transfer, PTU latching fault, or PTU local fault. The method mayfurther include receiving a first message from the first device on acommunication interface. The method may include extracting device dataencoded in the first message. The determining to transition the seconddevice may further comprise determining a first message is not receivedfrom the first device within a predetermined time; and determining thesecond operating mode is at least one of a power transmitting unit (PTU)latching fault or a PTU local fault mode. The communication interface isin accordance with Bluetooth low energy (BLE), near field communication(NFC), in-band modulation, or Wi-Fi. The extracted device data includeone or more power receiving unit (PRU) static data, wherein the PRUstatic data includes at least in part an NFC receiver bit. Thedetermining to transition the device may further comprise determiningthe NFC receiver bit is set to a first value; and determining the secondoperating mode is at least one of a power transmitting unit (PTU)latching fault or a PTU local fault mode. The method may further includedetermining the NFC receiver bit is set to a second value. The methodmay include determining an operating mode of the device is a powertransmitting unit (PTU) latching fault mode or a PTU local fault mode.The method may include transitioning the operating mode of the devicefrom the PTU latching fault mode or the PTU local fault mode to at leastone of a PTU power save, a PTU low power, or a PTU power transfer.

Certain aspects of the disclosure are described above with reference toblock and flow diagrams of systems, methods, apparatuses, and/orcomputer program products according to various implementations. It willbe understood that one or more blocks of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and the flowdiagrams, respectively, may be implemented by computer-executableprogram instructions. Likewise, some blocks of the block diagrams andflow diagrams may not necessarily need to be performed in the orderpresented, or may not necessarily need to be performed at all, accordingto some implementations.

These computer-executable program instructions may be loaded onto aspecial-purpose computer or other particular machine, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable storage media or memory that may direct acomputer or other programmable data processing apparatus to function ina particular manner, such that the instructions stored in thecomputer-readable storage media produce an article of manufactureincluding instruction means that implement one or more functionsspecified in the flow diagram block or blocks. As an example, certainimplementations may provide for a computer program product, comprising acomputer-readable storage medium having a computer-readable program codeor program instructions implemented therein, said computer-readableprogram code adapted to be executed to implement one or more functionsspecified in the flow diagram block or blocks. The computer programinstructions may also be loaded onto a computer or other programmabledata processing apparatus to cause a series of operational elements orsteps to be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide elementsor steps for implementing the functions specified in the flow diagramblock or blocks.

Accordingly, blocks of the block diagrams and flow diagrams supportcombinations of means for performing the specified functions,combinations of elements or steps for performing the specified functionsand program instruction means for performing the specified functions. Itwill also be understood that each block of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and flowdiagrams, may be implemented by special-purpose, hardware-based computersystems that perform the specified functions, elements or steps, orcombinations of special-purpose hardware and computer instructions.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainimplementations could include, while other implementations do notinclude, certain features, elements, and/or operations. Thus, suchconditional language is not generally intended to imply that features,elements, and/or operations are in any way required for one or moreimplementations or that one or more implementations necessarily includelogic for deciding, with or without user input or prompting, whetherthese features, elements, and/or operations are included or are to beperformed in any particular implementation.

Many modifications and other implementations of the disclosure set forthherein will be apparent having the benefit of the teachings presented inthe foregoing descriptions and the associated drawings. Therefore, it isto be understood that the disclosure is not to be limited to thespecific implementations disclosed and that modifications and otherimplementations are intended to be included within the scope of theappended claims. Although specific terms are employed herein, they areused in a generic and descriptive sense only and not for purposes oflimitation.

What is claimed is:
 1. A device, comprising: at least one memory thatstores computer-executable instructions; and at least one processor ofone or more processors configured to access the at least one memory,wherein the at least one processor is configured to execute thecomputer-executable instructions to: detect a presence of a near fieldcommunication (NFC) device in proximity to a charging area of thedevice; determine the NFC device is associated with a first device;identify an NFC receiver bit indicating a protection status of the NFCdevice; and determine to transition the device from a first operatingmode to a second operating mode based at least in part on the NFCreceiver bit and the presence of the NFC device.
 2. The device of claim1, wherein the first operating mode and the second operating modeinclude at least in part a power transmitting unit (PTU) power save, aPTU low power, a PTU power transfer, a PTU latching fault, or a PTUlocal fault.
 3. The device of claim 1, wherein the at least oneprocessor is further configured to execute the computer-executableinstructions to: receive a first message from the first device on acommunication interface; and extract device data encoded in the firstmessage.
 4. The device of claim 3, wherein the communication interfaceis in accordance with bluetooth low energy (BLE), near fieldcommunication (NFC), in-band modulation, or Wi-Fi.
 5. The device ofclaim 3, wherein the extracted device data includes one or more powerreceiving unit (PRU) static data, and wherein the PRU static dataincludes at least in part the NFC receiver bit.
 6. The device of claim5, wherein the instructions to determine to transition the devicefurther includes the instructions to: determine the NFC receiver bit isset to a first value; and determine the second operating mode is atleast one of a power transmitting unit (PTU) latching fault or a PTUlocal fault mode.
 7. The device of claim 5, wherein the at least oneprocessor is further configured to execute the computer-executableinstructions to: determine the NFC receiver bit is set to a secondvalue, wherein the instructions to determine to transition the devicecomprise executing the instructions to: determine that the firstoperating mode of the device is a power transmitting unit (PTU) latchingfault mode or a PTU local fault mode; and transition the first operatingmode of the device from the PTU latching fault mode or the PTU localfault mode to at least one of a PTU power save, a PTU low power, or aPTU power transfer.
 8. The device of claim 1, wherein the instructionsto determine to transition the device further include the instructionsto: determine a first message is not received from the first devicewithin a predetermined time; and determine the second operating mode isat least one of a power transmitting unit (PTU) latching fault or a PTUlocal fault mode.
 9. The device of claim 1, further comprising atransceiver configured to transmit and receive wireless signals.
 10. Thedevice of claim 9, further comprising one or more antennas coupled tothe transceiver.
 11. A non-transitory computer-readable medium storingcomputer-executable instructions which, when executed by a processor,cause the processor to perform operations comprising: determining apresence of a power transmitting unit (PTU); determining one or moredevice data, including a near field communication (NFC) receiver bitindicating whether an NFC device is protected; encoding the one or moredevice data into a first message; and causing to send the first messageto the PTU on a communication interface.
 12. The non-transitorycomputer-readable medium of claim 11, wherein the communicationinterface is in accordance with bluetooth low energy (BLE), near fieldcommunication (NFC), in-band modulation, or Wi-Fi.
 13. Thenon-transitory computer-readable medium of claim 11, wherein the PTUincludes a wireless charging surface.
 14. The non-transitorycomputer-readable medium of claim 11, wherein the computer-executableinstructions cause the processor to further perform operationscomprising encoding the NFC receiver bit based on an association with afirst NFC device.
 15. The non-transitory computer-readable medium ofclaim 14, wherein the computer-executable instructions cause theprocessor to further perform operations comprising setting the NFCreceiver bit to indicate that the NFC device is protected.
 16. Thenon-transitory computer-readable medium of claim 14, wherein thecomputer-executable instructions cause the processor to further performoperations comprising setting the NFC receiver bit to indicate that theNFC device is not protected.
 17. A method comprising: detecting, by atleast one processor, a presence of a near field communication (NFC)device in proximity to a charging area of a charging device; receiving,by the at least one processor, a first message from a device on acommunication interface, wherein the first message comprises an NFCreceiver bit indicating a protection status of the NFC device;determining, by the at least one processor, the NFC device is associatedwith the device; and determining, by the at least one processor, totransition the charging device from a first operating mode to a secondoperating mode based at least in part on detecting the presence of theNFC device and on the NFC receiver bit.
 18. The method of claim 17,wherein the first operating mode and the second operating mode includeat least in part a power transmitting unit (PTU) power save, a PTU lowpower, a PTU power transfer, a PTU latching fault, or PTU local fault.19. The method of claim 18, wherein determining to transition thecharging device further comprises: determining a first message is notreceived from the device within a predetermined time; and determiningthe second operating mode is at least one of a power transmitting unit(PTU) latching fault or a PTU local fault mode.
 20. The method of claim17, further comprising: receiving a first message from the first deviceon a communication interface; and extracting device data encoded in thefirst message.